What changed

• Added the single npm run launch:v0 command that runs indexer fixtures, verifier fixtures, the no-value devnet handoff, hardware validation, and FlowMemory generation end-to-end.
• Added canonical Flow Memory JSON schemas for MemorySignal, MemoryReceipt, RootfieldBundle, AgentMemoryView, and RootflowTransition.
• Added a FlowMemory service that creates concrete MemorySignal, MemoryReceipt, RootflowTransition, RootfieldBundle, and AgentMemoryView outputs from services/devnet/hardware fixtures.
• Regenerated dashboard fixtures and added a Flow Memory dashboard view fed by the generated launch-core data.
• Expanded GitHub Actions into area-specific CI for repo hygiene, contracts, services, launch core, crypto, dashboard, devnet, and hardware.

Why

FlowMemory needed a coherent local/testnet-ready V0 path for launch-critical Rootflow and Flow Memory state, instead of isolated pieces that only looked complete separately.

Validation already run locally

• npm run launch:v0
• npm test
• npm run e2e
• forge test
• npm test, npm run validate:vectors, and python validate_test_vectors.py in crypto/
• npm test and npm run build in apps/dashboard/
• cargo test --manifest-path crates/flowmemory-devnet/Cargo.toml
• python hardware/simulator/flowrouter_sim.py --validate-file hardware/fixtures/flowrouter_sample_seed42.json

Boundaries

This is local/test V0 launch-core integration. It does not claim production L1 readiness, Base mainnet readiness, full trustless verification, free storage, or AI running on-chain.